home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Gold Medal Software 3
/
Gold Medal Software - Volume 3 (Gold Medal) (1994).iso
/
utils1
/
copyq313.arj
/
WHATS.NEW
< prev
Wrap
Text File
|
1994-03-28
|
4KB
|
86 lines
What's New in CopyQM 3.13
Sydex, Inc.
P.O. Box 5700
Eugene, OR 97405
(503) 683-6033
March, 1994
CopyQM Plus now creates self-extracting image files directly, without
the use of MAKESXD. The SELFEXTRACT (abbreviated SELF) keyword, when
used with RECORD, causes a self-extracting file to be recorded.
MAKESXD now does its work in a single pass, without any additional disk
space required for temporary files.
BIOS support has been improved to accomodate a few less-IBM-conforming
BIOS sets.
Code has been added to enabled interrupts at critical points. We've seen
some BIOS code that doesn't seem to re-enable interrupts after they've
been disabled.
Support has been improved for 2.88M drives and controllers. However,
CopyQM requires that 2.88M drives be jumpered for auto media-sensing
to work with the DIRECT diskette controller access modes. If your
2.88M drives are not not jumpered in this manner, you can either reset
the jumpers or use BIOS access.
The SCANDISK utility in MS-DOS 6.2 sometimes reports a spurious boot-
sector and/or FAT error on diskettes generated with the CONVERT= option,
though MS-DOS CHKDSK finds no problem. We've traced this to SCANDISK's
insistence on a certain media byte for a given media type. Interestingly,
in Microsoft's own words: "Beginning with DOS 2.x, the usefulness of the
disk ID byte in the FAT was reduced and it now considered meaningless..."
Not being ones to argue a minor point, we now insert the proper media
media byte in CONVERT-ed diskettes and SCANDISK is happy. Sigh...
What's New in CopyQM 3.12
CopyQM 3.12 contains a few minor changes to version 3.11:
1. Support for the E-Ten Chinese language system has been
incorporated. Users who use other double-byte systems
can force the use of non-extended codes by means of the
/7BIT command-line switch on any of the CopyQM product
set.
2. A bug occurred when a BLIND mode copy was attempted where
FIRST= did not equal 1. Only one sector per track would
be seen when CopyQM was run in Direct hardware access mode.
3. A few Windows API calls have been added to the Direct I/O
routines. CopyQM should run as a background task in direct
hardware controller access mode under Windows 3.1. However,
IBM OS/2's implementation of Windows and their DOS box appear
to ignore these API calls, so running as a background task in
OS/2 will still result in occasional "DRIVE NOT READY" errors.
4. Normally, CopyQM and its utilities will access the screen memory
directly in order to draw displays as quickly as is possible.
However, if the following switch is used, CopyQM and its
utilities will use the video BIOS to create screen displays:
/CRTBIOS
This can be abbreviated to /CR. For example, if a copy using
drives A: and B: is to be performed, the following command line
could be used:
COPYQM A: B: /CRTBIOS
Similarly, all CopyQM utilities, including CQMENU, CINSTALL,
ICOMMENT, MAKESXD (CopyQM Plus only), DRMAINT (CopyQM Plus only)
will accept the /CRTBIOS switch. The configuration viewer,
VIEWCONF, accepts this switch, but ignores it, as VIEWCONF
always uses the CRT BIOS.
Text-to-speech translator users may want to experiment with
the switches /7BIT and /MONO to reduce the number of non-text
characters on the screen. The /7BIT switch forces the use of
the lower 128 codes in the ASCII set; that is, line-drawing and
character graphics are not used. The /MONO switch forces use of
a monochrome display set.